System, Method, and Device for Routing Calls Using a Distributed Mobile Architecture

ABSTRACT

Methods and devices for routing communications between distributed management architecture (DMA) servers using DMA gateways are disclosed. Communications information is received at a first DMA gateway for a communications network accessible by a second DMA gateway. The communications information indicates one or more devices that are accessible by one of a DMA server and a legacy communications network. The first DMA gateway and the second DMA gateway participate in a DMA gateway communications network. The communications information is stored in a home DMA register of the first DMA gateway. A communication is received at the first DMA gateway for a target device indicated by the communications information to be served by the second DMA gateway. The communication is routed from the first DMA gateway to the target device by relaying the communication from the first DMA gateway to the second DMA gateway via the DMA gateway communications network.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to distributed mobilecommunications systems.

BACKGROUND

Access to basic telephony service is particularly important for ruraland isolated communities. Telephony access allows small-scaleenterprises, cooperatives, and farmers to obtain accurate information onfair prices for their products and to access regional and nationalmarkets. Access also reduces the cost of transportation and supports thelocal tourist industry. By bringing markets to people viatelecommunications, rather than forcing people to leave in search ofmarkets, urban migration is reduced and greater income and employmentpotential are generated in rural areas.

Unfortunately, the last decade of the telecommunications boom has notalleviated the disparities between urban and rural communities. Theaverage imbalance, in terms of telephone penetration, in Asia, forexample, is over ten to one and is often as high as twenty to one. Thismeans that a country whose urban markets have a penetration of four (4)telephone lines per one-hundred (100) inhabitants, e.g., India andPakistan, has a rural penetration of less than 0.2 per one-hundred(100). The situation is more acute in most African countries and in someparts of Latin America. By comparison, the disparity in average incomelevel between urban and rural residents in the developing world isusually less than 4 to 1.

Current telephone systems are expensive to deploy. For example, atypical cellular system that includes a mobile switching center (MSC), abase station controller (BSC), and a home location register/visitorlocation register (HLR/VLR) can cost over $2.0 million. Moreover, such asystem may require a minimum of ten thousand users in order to beeconomically viable. In many rural areas, the population is not largeenough to support the installation of such a system. Further, in manycases, the conditions in which the equipment (e.g., the MSC, BSC, andHLR/VLR) are to be operated are extremely harsh and environmentallyprohibitive. An alternative to such a cellular system can include awired system, but the costs associated with deploying and maintainingland lines are too high for certain rural areas.

In deploying telephone systems in such situations, a further concern ishow to expand an existing telephone system or implement a new phonesystem capable of operating with existing telephone systems. Forexample, it may be desirable to allow communications with users servicedby existing public switched telephone network (PSTN) services, Voiceover Internet Protocol (VoIP) systems, wireless communications systems,and other systems. Providing compatibility between these systemspresents a challenge in itself. Moreover, because some of these systemsmay be deployed in rural or other remote areas, providing a mediumthrough which newly deployed systems can communicate with one anotherpresents a concern.

Accordingly, there exists a need for an improved communications systemthat is relatively inexpensive to deploy and relatively inexpensive tooperate, as well as able to integrate different communications systems.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is pointed out with particularity in the appendedclaims. However, other features are described in the following detaileddescription in conjunction with the accompanying drawings in which:

FIG. 1 is a view of a particular illustrative embodiment of adistributed management architecture (DMA) server having a firstillustrative form factor;

FIG. 2 is a view of another particular illustrative embodiment of analternative embodiment of a DMA server having a second illustrative formfactor;

FIG. 3 is a diagram of another particular illustrative embodiment of analternative embodiment of a DMA server having a third illustrative formfactor;

FIG. 4 is a diagram of a particular illustrative embodiment of adistributed and associative communications system;

FIG. 5 is a block diagram of a particular illustrative embodiment of aDMA server;

FIG. 6 is a diagram of a particular illustrative embodiment of a networkincorporating a plurality of DMA gateways linking a plurality of DMAservers and a legacy network;

FIG. 7 is a diagram of a particular illustrative embodiment of a networkincorporating a plurality of satellite-based DMA gateways linking aplurality of DMA servers and a legacy network;

FIG. 8 is a diagram of a particular illustrative embodiment of a networkincorporating a DMA gateway linking a plurality of satellite-based DMAservers and ground-based DMA servers;

FIG. 9 is a diagram of a particular illustrative embodiment of a networkincorporating a plurality of satellite-based and ground-based DMAgateways linking a plurality of satellite-based and ground-based DMAservers;

FIG. 10 is a diagram of a particular illustrative embodiment of anetwork incorporating a plurality of DMA gateways and a plurality oflegacy networks utilizing a central register database for communicationsdevices accessible within the network;

FIG. 11 is a block diagram of a particular illustrative embodiment of aDMA gateway;

FIG. 12 is a diagram of a particular illustrative embodiment of anexemplary data structure used by a DMA gateway for maintaininginformation about communications devices accessible through othergateways;

FIG. 13 is a diagram of a particular illustrative embodiment of anexemplary structure maintained in a central database accessible by DMAgateways to maintain information about communications devices accessiblethroughout a network;

FIG. 14 is a flow chart to illustrate a particular illustrativeembodiment of the use of information about accessible networks anddevices for routing communications between DMA gateways; and

FIG. 15 is a flow chart to illustrate a particular illustrativeembodiment of a selective routing of a communication by a DMA gatewayvia a private Internet Protocol network or a gateway network.

DETAILED DESCRIPTION OF THE DRAWINGS

Methods and devices for routing communications between distributedmanagement architecture (DMA) servers using DMA gateways are disclosed.Communications information is received at a first DMA gateway for acommunications network accessible by a second DMA gateway. Thecommunications information indicates one or more devices that areaccessible by one of a DMA server and a legacy communications network.The first DMA gateway and the second DMA gateway participate in a DMAgateway communications network. The communications information is storedin a home DMA register of the first DMA gateway. A communication isreceived at the first DMA gateway for a target device indicated by thecommunications information to be served by the second DMA gateway. Thecommunication is routed from the first DMA gateway to the target deviceby relaying the communication from the first DMA gateway to the secondDMA gateway via the DMA gateway communications network.

In a particular embodiment, a first distributed mobile architecture(DMA) gateway includes a number of interfaces. A first interface isadapted to communicate with a legacy communications network. A secondinterface is adapted to communicate with a private Internet Protocol(IP) network. A third interface is adapted to communicate with a DMAgateway communications network. The gateway also includes a serverhaving logic adapted to receive legacy network information from a secondDMA gateway, the legacy network information indicating that the legacycommunications network is in a communications range of the second DMAgateway. The DMA gateway forwards information associated with acommunication received from a DMA server via the second interface to thesecond DMA gateway via the third interface. The call is placed to adestination device accessible via the legacy communications network.

In another particular embodiment, first routing instructions at a firstdistributed mobile architecture (DMA) server from a first DMA gatewaywhen the first DMA server is in a first service area of the first DMAgateway. The first DMA gateway comprises a first orbiting satellite. Afirst call received at the first DMA server from a first mobilecommunications device via a wireless transceiver integrated with thefirst DMA server is sent to the first DMA gateway via a private InternetProtocol (IP) network according to the first routing instructions. Thefirst call is placed to a destination device accessible via a legacycommunications network, the legacy communications network accessible viathe first DMA gateway.

In another embodiment, a distributed mobile architecture (DMA) server iscoupled to a wireless transceiver. The DMA server includes a firstinterface adapted to communicate with a private Internet Protocol (IP)network and a second interface adapted to communicate with a satellitecommunications network. The DMA server includes a server having logicadapted to receive a call from a mobile communications device via thewireless transceiver and send call information related to the call to aDMA gateway. The DMA gateway comprises an orbiting satellite. The callis placed to a destination device accessible via a legacy communicationsnetwork, the legacy communications network accessible via the DMAgateway.

In yet another embodiment, an orbiting satellite includes a firstinterface adapted to communicate with a legacy communications networkand a second interface adapted to communicate with a private InternetProtocol (IP) network. The satellite also includes a server having logicadapted to receive a call via the first interface. The call is placed toa first mobile communications device accessible to a first distributedmobile architecture (DMA) server. The call is then routed to the firstDMA server via the second interface, wherein the first DMA serverincludes a wireless transceiver to communicate with the first mobilecommunications device.

According to the present disclosure, one or more of the communicationsdevices between which a communication, such as a voice communicationand/or a data communication, participates in a communications networkvia a DMA server. A DMA server enables the deployment or expansion of acommunications network to, for example, rural areas where remoteness ofthe area to be served or a relatively small customer base to be servedmake the installation of a conventional telephone system impractical orotherwise undesirable. As further described below according toembodiments of this disclosure, while one or more DMA servers maycommunicate with one another over a private IP network, when a privateIP network is not available, the DMA servers may communicate through aplurality of DMA gateways that communicate with one another through agateway communications network. For example, the DMA gateways may beimplemented as orbiting satellites that participate in a gatewaycommunications network that includes a satellite communications network.

In introducing the operation of DMA gateways, exemplary embodiments ofDMA servers and their operation are described below.

Referring to FIG. 1, a DMA server is shown and is generally designated100. As illustrated in FIG. 1, the DMA server 100 includes a base 102and a lid 104. As shown, the lid 104 is attached to the base by a firstlid hinge 106 and a second lid hinge 108. In a particular embodiment,the lid 104 can be rotated about the first lid hinge 106 and the secondlid hinge 108 between an open position, shown in FIG. 1, and a closedposition (not shown) in which the lid 104 overlays the base 102 and theDMA server 100 is essentially shaped like a box or a briefcase.

As indicated in FIG. 1, the base 102 has a length 110, a width 112 and aheight 114. FIG. 1 shows that the DMA server 100 includes a keyboardinput device 116 that is incorporated in an upper surface of the base102. Further, the DMA server 100 includes a mouse input device 118 thatis also incorporated into the upper surface of the base 102. In aparticular embodiment, the mouse input device 118 is a touch mouse inputdevice 118. Additionally, the DMA server 100 includes a left side button120 and a right side button 122. In a particular embodiment, the leftside button 120 can be used to perform left-click functionalityassociated with the mouse input device 118. Moreover, the right sidebutton 122 can be used to perform right-click functionality associatedwith the mouse input device 118.

FIG. 1 further indicates that the base 102 of the DMA server 100 isformed with a vent 124 to permit air exchange with the interior of thebase 102 of the DMA server 100 and to facilitate cooling of theelectronic components of the DMA server 100 housed within the base 102.Moreover, the base 102 of the DMA server 100 includes a handle 126 thatis attached to the base 102 via a first handle hinge 128 and a secondhandle hinge 130. The base 102 also includes a pair of latch engagementnotches 132.

As shown in FIG. 1, the lid 104 includes a flat panel display 134incorporated therein. When the lid 104 is closed, the display 134 isadjacent to the keyboard 116. Moreover, when the lid 104 is closed, thelid 104 and the base 102 cooperate to protect the display 134, thekeyboard 116, the mouse 118, and the buttons 120, 122. FIG. 1 alsodepicts a latch 136 that is incorporated into the lid 104. When the lid104 is closed, the latch 136 can engage the latch engagement notches 132in order to lock the lid in the closed position. As depicted in FIG. 1,an antenna 138 is incorporated into the lid 104. The antenna 138 can beextended during operation and retracted when the DMA server 100 is notoperating.

In a particular embodiment, the length 110 of the base 102 is 31.0centimeters. Further, in a particular embodiment, the width 112 of thebase 102 is 25.5 centimeters. Additionally, in a particular embodiment,the height 114 of the base 102 with the lid 104 in the closed positionis 7.0 centimeters. Accordingly, the DMA server 100 has a total volumeof 5,533.5 centimeters cubed and a footprint area of 790.5 centimeterssquared. Further, in a particular embodiment, the DMA server 100 weighsapproximately 5.8 kilograms (kg). As such, in a particular embodiment,the DMA server 100 has a total volume that is less than 6,000centimeters cubed, a footprint area that is less than 800 centimeterssquared, and a weight that is less than 6.0 kilograms.

In a particular embodiment, the DMA server 100 is relatively rugged.Particularly, the DMA server 100 is operable in a temperature range fromnegative twenty degrees Celsius to positive fifty-five degrees Celsius(−20° C. to 55° C.). Also, the DMA server 100 is substantially shockresistant and can withstand a one meter drop. Further, the DMA server100 is substantially weather resistant, substantially dust resistant,and substantially sand resistant. The DMA server 100 is portable and itcan be mounted in a vehicle or carried like a brief case. Further,multiple DMA servers 100 can be deployed as described herein.

FIG. 2 depicts an alternative embodiment of a distributed managementarchitecture (DMA) server that is generally designated 200. As shown inFIG. 2, the DMA server 200 includes a base 202 and a lid 204 that iscoupled to the base 202 via a plurality of fasteners (not shown).Additionally, the DMA server 200 has a length 208, a width 210, and aheight 212. Further, the base 202 of the DMA server 200 includes a firstvent 214, a second vent 216, and a third vent 218. In a particularembodiment, the vents 214, 216, 218 permit air exchange with theinterior of the base 202 of the DMA server 200 and facilitate cooling ofthe electronic components of the DMA server 200 housed within the base202. As shown in FIG. 2, the DMA server 200 includes an access window220. One or more interfaces 222, e.g., wires can be accessed via theaccess window 220 and coupled to a base transceiver station (BTS) duringdeployment of the DMA server 200. As shown in FIG. 2, the DMA server 200can be mounted within a vehicle 224. Further, multiple DMA servers 200can be deployed as described herein.

In a particular embodiment, the length 208 of the base 202 is 92.0centimeters. Further, in a particular embodiment, the width 210 of thebase 202 is 45.0 centimeters. Additionally, in a particular embodiment,the height 212 of the base 202 is 34.0 centimeters. Accordingly, the DMAserver 200 has a total volume of approximately 140,760 centimeters cubedand a footprint area of approximately 4,140 centimeters squared.Further, in a particular embodiment, the DMA server 200 weighsapproximately 48 kilograms (kg). As such, in a particular embodiment,the DMA server 100 has a total volume that is less than 150,000centimeters cubed, a footprint area that is less than 5,000 centimeterssquared, and a weight that is less than 50.0 kilograms.

FIG. 3 illustrates another alternative embodiment of a distributedmanagement architecture (DMA) server that is generally designated 300.As depicted in FIG. 3, the DMA server 300 includes a housing 302 thathas a length 304, a width 306, and a height 308. Additionally, thehousing 302 can be formed with a first vent 310 and a second vent 312.In a particular embodiment, the vents 310, 312 permit air exchange withthe interior of the housing 302 of the DMA server 300 and facilitatecooling of the electronic components of the DMA server 300 within thehousing 302.

As shown in FIG. 3, at least one side of the housing 302 is formed witha rib 314 to enable the DMA server 300 to be slid into a server rack(not shown). Further, the DMA server 300 includes a clip 316 that iscoupled to the housing 302 via a fastener, e.g., a bolt. The clip 316can be engaged with a server rack (not shown) to prevent the DMA server300 from unintentionally sliding out of the server rack (not shown).

In a particular embodiment, the length 304 of the housing 302 isapproximately 76.2 centimeters. Further, in a particular embodiment, thewidth 306 of the housing 302 is approximately 48.2 centimeters.Additionally, in a particular embodiment, the height 308 of the housing302 is approximately 4.3 centimeters. Accordingly, the DMA server 300has a total volume of approximately 15,756.5 centimeters cubed and afootprint area of approximately 3,672.9 centimeters squared. Further, ina particular embodiment, the DMA server 300 weighs approximately 17.7kilograms (kg). Also, in a particular embodiment, the DMA server 300 isstackable in order to support various capacity requirements. As such, ina particular embodiment, the DMA server 100 has a total volume that isless than 16,000 centimeters cubed, a footprint area that is less than4,000 centimeters squared, and a weight that is less than 20.0kilograms.

The description of embodiments of DMA servers with reference to FIGS.1-3 are provided for illustration, not limitation. DMA servers also maybe embodied in any other suitable form. For example, as describedfurther below, a DMA server may be incorporated within an orbitingsatellite that communicates with DMA gateways and other devices viasatellite and ground-based communication networks.

FIG. 4 illustrates a non-limiting, exemplary embodiment of adistributive and associated telecommunications system generallydesignated 400. As depicted in FIG. 4, the system 400 includes fourcellular coverage sites 402. Each coverage site 402 includes an antenna404. In one embodiment, the antenna 404 is connected to a transceiverbelonging to a base transceiver station (BTS) and the BTS is a 3-sectorBTS. FIG. 4 also indicates that a distributed mobile architecture (DMA)server 406 (abbreviated in FIG. 4 and figures as “DMAS”) can beconnected to each antenna 404. In one embodiment, each DMA server 406 isphysically and directly connected to its respective antenna 404, e.g.,by a wire or cable 408. Further, in an illustrative embodiment, the DMAservers 406 can be any of the DMA servers shown in FIG. 1, FIG. 2, andFIG. 3.

As illustrated in FIG. 4, each DMA server 406 is interconnected with theother DMA servers 406 via an Internet protocol network 410. As such,there exists a peer-to-peer connection 412 between each DMA server 406in the system 400. As described in detail below, the DMA servers 406 canhandle telephony traffic that is communicated at each antenna 404. Forexample, the DMA servers 406 can switch and route calls received viaeach antenna 404. Additionally, the DMA servers 406 can hand-off callsto each other as mobile communications devices move around and betweenthe cellular coverage sites 402. The DMA servers 406 can communicatewith each other via the IP network 410 and can further transmit calls toeach other via the IP network 410. It should be understood that morethan four cellular coverage sites 402 can be included in the system andthat the inclusion of only four cellular coverage sites 402 in FIG. 4 ismerely for clarity and explanation purposes.

Within the distributed and associative telecommunications system 400 thecontrolling logic can be distributed and de-centralized. Moreover, thewireless coverage provided by the disclosed system 400 is self-healingand redundant. In other words, due to the interconnectivity via the IPnetwork 410, if one or more of the DMA servers 406 loses powers, fails,or is otherwise inoperable, telephony traffic handled by the inoperableDMA server 406 can re-routed to one of the remaining operable DMAservers 406. Additionally, user data stored in a database, e.g., a homelocator resource (HLR) or a visitor locator resource (VLR), can bedistributed equally and fully among all of the DMA servers 406. It canalso be appreciated that new cellular coverage sites can be easily addedto the system 400 as the demand for users increases. Specifically, a DMAserver can be deployed as described below, connected to an antenna,connected to the IP network, and activated to provide cellular coveragein a new area.

FIG. 5 shows an exemplary, non-limiting, detailed embodiment of a DMAserver, e.g., one of the DMA servers 406 described in conjunction withFIG. 4. Further, any of the DMA servers 100, 200, 300 shown in FIG. 1,FIG. 2, and FIG. 3 can include the components depicted in FIG. 5 anddescribed herein.

In a particular embodiment, the DMA server 406 is essentially aprocessor, or computer, having a housing and a computer readable medium500 that is disposed therein. A power supply 502 can also be disposedwithin the housing of the DMA server 406 in order to provide power tothe DMA server 406. The power supply 502 can be a rechargeable batterydisposed within the DMA server 406 or it can be external to the DMAserver 406, i.e., a standard power outlet. Moreover, a cooling system504, e.g., a fan with a thermostat, can be within the DMA server 406 inorder to keep the DMA server 406 from overheating. In an alternativeembodiment, the DMA server 406 can be a single board processor that doesnot require a fan.

As depicted in FIG. 5, the DMA server 406 may include a mobile switchingcenter (MSC) module 506 and a base station controller (BSC) module 508embedded within the computer readable medium 500. In an exemplary,non-limiting embodiment, the MSC module 506 can include a gatekeeper(GK) 510 that is connected to several gateways. For example, a circuitgateway (CGW) 512 can be connected to the GK 510 and can provideconnectivity to an integrated services digital network/public switchedtelephone network (ISDN/PSTN) interface 514. The CGW 512 can provide acircuit switched to packet data conversion. In an exemplary,non-limiting embodiment, the PSTN portion of the ISDN/PSTN interface 514can be an inter-office interface that uses the Bellcore industrystandard ISDN user part (ISUP) signaling on a signaling system seven(SS7) link set. Moreover, the voice trunks on this interface can betimeslots on a T1 connection. Inbound and outbound voice calls can besupported on the ISDN portion of the ISDN/PSTN interface 514.

As further illustrated in FIG. 5, a packet data server node (PDSN)gateway 516 for CDMA, or a Gateway GPRS Support Node (GGSN) for GlobalSystem for Mobile Communication (GSM), and a Session Initiation Protocol(SIP) gateway 518 can also be connected to the GK 510. The PDSN gateway516 and the SIP gateway 518 can provide connectivity to an IP interface520. Further, the PDSN gateway 516 or a GGSN can establish a reversetunnel with the PDSN or GGSN gateway 516 using generic routingencapsulation (GRE). Moreover, the PDSN gateway 516, or GGSN, canimplement the Pseudo Random Function (PRF)/Foreign Agent (FA)functionality of the DMA server 406 which supports mobile IP functions.

FIG. 5 further shows an SS7 gateway 522 that provides connectivity to anAmerican National Standards Institute 41 (ANSI-41) and GSM MobileApplication Part (MAP) interface 524. In a particular embodiment, theANSI-41 interface can be an SS7 TCAP/SCCP interface on the same SS7 linkset used for ISUP signaling. The same SS7 point code can be used toidentify the DMA server 406 in the ANSI-41 network. The ANSI-41interface can be used for roamer registration. Further, in an exemplary,non-limiting embodiment, the GSM MAP interface can be an SS7 TCAP/SCCPinterface on the same SS7 link set used for ISUP signaling. It can beappreciated that there are different protocols of MAP from MAP/B toMAP/I, but in the illustrative embodiment, the different MAP/x protocolsare not stacked—they are used independently. As described with referenceto FIG. 11, the SS7 interface may be included in either the DMA server406 or the DMA gateway 1102.

As depicted in FIG. 5, a media gateway 526 can also be coupled to the GK510. In an exemplary, non-limiting embodiment, the media gateway 526 caninclude cellular transcoders, one or more intranet gateways,conferencing bridges, and group calling functionality. Further, anauthentication, authorization, and accounting (AAA) module 528 can becoupled to the GK 510. In an exemplary, non-limiting embodiment, thereare three levels of authentication management. The highest level is foradministration, the mid-level is for operations, and the lowest level isfor normal users. The functions of the AAA module 528 can be included inthe user level.

In an exemplary, non-limiting embodiment, the GK 510 can act as an AAAserver and a feather server to support advanced supplementary service,short message service, etc. Moreover, the GK 510 can act as a callmanager and can support ISUP and PSTN function calls. Additionally, theGK 510 can act as a signal gateway, e.g., IP to SS7 inter-working, ISUP,GSM MAP or ANSI-41 to PSTN and ANSI-42/GSM. The GK 510 can also functionas a data call server.

As illustrated in FIG. 5, the BSC module 508 includes a cellular radionetwork controller (CRNC) 530 and a cellular selection/distribution unit(CSDU) 532 that are connected to a call protocol controller (CPC) 534.In turn, the CPC 534 can be connected to a plurality of base transceiverstations (BTSs) 536. Specifically, the DMA server 406 includes a BTSinterface 538 at the CPC 534 that can be physically and directlyconnected to the BTSs 536. The CRNC 530 can provide cellular radioresource management and cellular call control. The CSDU 532 can provideFundamental Channel (FCH) soft handoff and distribution, Link AccessControl (LAC) processing for inband signaling, multiplexer (MUX)functions, and centralized power control. Further, the CPC 534 canconvert a T1 or E1 message or ATM interface to a data packet message. Ina particular embodiment, each BTS 536 supports signals and traffic up tothe front point of the CPC 534, e.g., up to the BTS interface 538.Further, in a particular embodiment, the CRNC 530, the CPC 534, the CSDU532 and the OAMP 540 can perform one or more of the functions of legacyBase Station Controllers (BSC).

In an exemplary, non-limiting embodiment, the BTS interface 538 can bean IS-95A OR IS-2000 interface over E1 or ATM, or the BTS interface 538can be a GSM BTS interface using MAP or customized application formobile network enhanced logic (CAMEL). In an illustrative embodiment,the CPC 534 can be connected to one or more BTSs 536. FIG. 5 furthershows that the BSC module 508 includes an operations, administration,maintenance, and provisioning (OAMP) module 540. In an exemplary,non-limiting embodiment, the OAMP module 540 can use simple networkmanagement protocol (SNMP) for operations interfaces. Further, the OAMPmodule 540 can include a JAVA user interface. The OAMP module 540 canalso include a software agent that is assigned to each component withinthe DMA server 406. The agents independently monitor their respectivecomponents. Moreover, each agent can provision its respective component.

When deployed in a network, such as illustrated in FIG. 4, embodimentsof DMA servers are configured to handle the handing off ofcommunications when, for example, a mobile device passes from a coveragesite 402 (FIG. 4) covered serviced by one DMA server 406 to anothercoverage site 402 serviced by another DMA server 406. As previouslydescribed, the DMA servers 406 participate in an IP network 410 throughwhich the communications are routed between the DMA servers 406.However, in not all cases will the DMA servers 406 be able toparticipate as peers in an IP network 410. For example, if one or moreof the coverage sites 402 are in rural locations or other locationsremote from other coverage sites 402, there may not be access to the IPnetwork 410 in the remote coverage sites 402. Accordingly, embodimentsof the present disclosure describe DMA gateways to enable DMA servers tocommunicate with one another when one or more of the DMA servers cannotparticipate directly in the IP network. In addition, embodiments of theDMA gateways also enable legacy networks and devices participating inthe legacy networks to communicate with devices serviced by one or moreof the DMA servers as further described below.

Because of the mobility of various forms of the DMA servers and devicesthat may communicate via these servers, as well as the DMA gatewaysdescribed below, the communications network accounts for the movement ofthese devices. In other words, as the devices move, informationregarding the accessibility of these devices and how communications arerouted among them is dynamic. Thus, even when such devices move duringthe course of a communication, information pertaining to the routing ofthe communication is updated to support continuation of thecommunication.

FIG. 6 illustrates a network 600 that includes a first DMA gateway(abbreviated as “DMAG” in FIG. 6 and other figures) 602 and a second DMAgateway 604 that communicate with each other over a DMA gateway network606. The DMA gateway network 606 may include a dedicated wired orwireless communication medium or be included within a network carryingother communications. The second DMA gateway 604 communicates with alegacy network that, for example, includes a public switched telephonenetwork 610 that services communication with wired, landline devicessuch as landline telephone 612. The DMA gateway also may enablecommunication with public IP networks that enable data communications,Voice over Internet Protocol (VoIP) communications, and othercommunications, as well as other types of legacy networks. Although apair of DMA gateways 602 and 604 and a single legacy network 610 areshown in FIG. 6, any number of DMA gateways and legacy networks mayparticipate in the network 600.

In addition to the DMA gateways 602 and 604 and the legacy network 610,the network 600 includes two groups of DMA servers in which the DMAservers communicate with each other over separate private IP networks.For example, in a first group communicating via a first private IPnetwork 620, three DMA servers 622, 624, and 626 communicate with eachother. In a second group communicating via a second private IP network640, three DMA servers 642, 644, and 646 communicate with each other.Two different groups each including three DMA servers are shown forillustration. However, it will be appreciated that any number of groupsof DMA servers could communicate with each other within each of thegroups, and any number of groups could be bridged using DMA gateways asdescribed below to enable communications between devices associated withdifferent DMA servers in different groups.

Each of the DMA servers may service a plurality of voice and/or datacommunications devices. For example, a first DMA server 622, through anassociated wireless transceiver, may service a plurality ofcommunications devices such as a first wireless telephone device 632. Aspreviously described with reference to FIG. 4, the first wirelesstelephone device 632 may communicate with devices serviced by other DMAservers that participate in the first private IP network 620. Thus, forexample, the first wireless telephone device 632 would be able to engagein voice and/or data communications with a second wireless telephonedevice 634 serviced by a second DMA server 624. Also, it should beappreciated that the second wireless telephone device may communicatewith other devices, such as a third wireless telephone device 636 thatis serviced by a same DMA server, such as the second DMA server 624.Although the DMA servers in FIG. 6 are only shown servicing wirelesstelephone devices, it should be appreciated that other devices, such ascomputers and other communication devices also may participate in thenetwork 600 by communicating through the DMA servers.

As shown in FIG. 6, the groups of DMA servers communicating via the twoprivate IP networks 620 and 640 are separate networks. The wirelesstelephone devices 632, 634, and 636 serviced by DMA servers 622 and 624participating in the first private IP network 620 do not have a networkconnection with any of the DMA servers 642, 644, and 646 thatcommunicate with each other via the second private IP network. Thus, afourth wireless telephone device 652 in communication with a fourth DMAserver 642 can communicate with a fifth wireless telephone device 654serviced by a fifth DMA server 644 because the DMA servers 642 and 644can communicate with each other via the second private IP network 640.Similarly, the sixth wireless telephone device 656 and the seventhwireless telephone device 658 can communicate with each other throughthe sixth DMA server 646 with which each communicates and each cancommunicate with the other wireless telephone devices 652 and 654serviced by the other DMA servers 642 and 644 participating in thesecond private IP network. However, without a bridge between the firstprivate IP network 620 and the second private IP network 640, neitherthe DMA servers nor the wireless telephone devices serviced by each ofthe private IP networks 620 and 640 can communicate with devicesserviced by the other private IP network. Similarly, neither the DMAservers nor the wireless telephone devices serviced by each of theprivate IP network 620 and 640 can communicate with the public switchedtelephone network 610 or any of the devices, such as the landlinetelephone device 612, serviced by the public switched telephone network610.

Embodiments of the present disclosure enable devices on separatenetworks to communicate with each other via DMA gateways that bridgeseparate network and communications systems. In the example of FIG. 6,the first private IP network 620 communicates with the first DMA gateway602 and the second private IP network 640 communicates with the secondDMA gateway 604. The DMA gateways 602 and 604 are configured to routecommunications from one private IP network to another and the DMAgateways 602 and 604 are in communication with each other via the DMAgateway network 606. As a result, the DMA gateways 602 and 604 can routecommunications from the DMA servers 622, 624, and 626 and the devicesthey service to the DMA servers 642, 644, and 646 and the devices theyservice and vice versa. Also, because the second DMA gateway is coupledwith the second public switched telephone network 640, the wirelesstelephone devices 652, 654, 656, and 658 and other devices serviced bythe DMA servers 642, 644, and 646 can communicate with the landlinetelephone device 612 and other devices serviced by the public switchedtelephone network 610. In short, the DMA gateways can providecommunications between wireless devices serviced by associated DMAservers and wired or wireless devices serviced by legacy networkscoupled with the DMA gateways.

To facilitate communications between devices serviced by differentnetworks, the DMA gateways 602 and 604 maintain information identifyingthe devices that each services. For example, when the first wirelesstelephone device 932 initiates a communication to the fourth wirelesstelephone device 952, the first DMA gateway 602 accesses dataidentifying what other DMA gateway, if any, services the fourth wirelesstelephone device and which DMA server or other network or deviceassociated with the first DMA gateway services the targeted fourthwireless telephone device 952. DMA gateways provide information to oneanother regarding the communications networks they service by exchangingregister data describing the networks they service. The register datadescribes devices for which the networks they service are the homenetwork as well as for what devices are visiting on their networks. Thisinformation is exchanged directly between the DMA gateways or through acentral database described further below with reference to FIG. 10.

A DMA server may associate itself with different DMA gateways. Forexample, as described with reference to FIGS. 1 and 2, a DMA server mayinclude a mobile device that is easily moved from one place to another.A mobile DMA server that communicates wirelessly with a private IPnetwork and the DMA gateway servicing that private IP network may moveout of communications range of a DMA gateway with which it waspreviously associated into communications range with another DMAgateway. For further example, for purposes of traffic management, faulttolerance, or other reasons, it may be desirable to reassociate a DMAserver previously associated with one DMA gateway to another DMAgateway. This reassociation may be initiated manually or automaticallyby the DMA server, the DMA gateway, or any combination thereof. Thus,for example, the fourth DMA server 642 may be reassociated with thefirst private IP network 620 and the first DMA gateway 602 servicing thefirst private IP network 620 as shown by the dashed line 660 in FIG. 6.Because the DMA gateways 602 and 604 bridge the private IP networks 620and 640, devices serviced by the fourth DMA server 642, such as thefourth wireless telephone device 652 may continue to communicate withthe wireless telephone devices 654, 656, and 658 serviced by the DMAservers 644 and 646 associated with the second private IP network 640.

The DMA gateways and DMA servers can be arrayed in any number of ways tofacilitate the deployment and proliferation of communications networks.For example, FIG. 7 illustrates a network 700 that includessatellite-based DMA gateways including a first satellite-based DMAgateway 702 and a second satellite-based DMA gateway 704. Thesatellite-based DMA gateways 702 and 704 are placed in orbits suitableto enable communications with ground-based private IP networks 720 and740 and a ground-based legacy network 710. The satellite-based DMAgateways 702 and 704 communicate with each other via a satellitecommunications network 706. The second satellite-based DMA gateway 704communicates with a legacy network, such as a public switched telephonenetwork 710, over a communications uplink 714 via the same satellitecommunications network 706 through which the satellite-based DMAgateways 702 and 704 communicate or another uplink communicationsmedium. The satellite-based DMA gateways 702 and 704 communicate withprivate IP networks 720 and 740 that may include ground-based private IPnetworks, via the same satellite communications network 706 or otheruplink communications media. An advantage of including satellite-basedDMA gateways is the ability to bridge DMA servers or groups of DMAservers with one another even though the DMA servers or groups of DMAservers may be disposed remotely from each other where ground-based DMAgateways or ground-based communications media between the DMA serversare overtaxed, unreliable, unavailable, or otherwise undesirable.

Using the satellite-based DMA gateways 702 and 704, communicationsbetween the DMA servers, the devices they serve, and the legacy networkoperates in a similar manner to the communications between devices asdescribed with reference to FIG. 6. A first group of DMA servers 722,724, and 726 communicate via a first private IP network 720. A firstwireless telephone device 732 in communication with a first DMA server722 is able to communicate with a second wire telephone device 734 incommunication with a second DMA server 724 via the first private IPnetwork 720. Further, the first wireless telephone device 732 isenabled, via the first DMA server 722 and the first private IP network720, to communicate with the first DMA gateway 702. Then, via thesatellite communications network 706, the first DMA gateway 702 is ableto communicate with the second DMA gateway 704 to enable communicationswith devices served by the second private IP network 740. Thus, the DMAgateways 702 and 704 allow the first wireless telephone device 732 tocommunicate with a third wireless telephone device 762 even though thewireless telephone devices 732 and 762 participate in separate privateIP networks 720 and 740. In addition, because the second DMA gateway 704is in communication with both the second private IP network 740 and thepublic switched telephone network 710, the second DMA gateway 704enables mobile-to-land communications between third wireless telephonedevice 762 and a wired landline device 712. The use of satellite-basedDMA gateways 702 and 704 enables this communication even a vastdistances separate the communication devices and there are little or noland-based communications networks between the devices.

FIG. 8 illustrates a communications network 800 in which, instead ofutilizing satellite-based DMA gateways, employs a ground-based DMAgateway 830 facilitating communications between satellite-based DMAservers 810 and 820. In areas where, for example, a ground-based DMAserver cannot be employed or the distance between wireless communicationdevices 812 and 814 is so large that one or more DMA servers may not beable to effectively service the wireless communication devices 812 and814, it may be desirable to enable communications with the deployment ofsatellite-based DMA servers such as DMA servers 810 and 820. In such acase, the wireless communications devices 812 and 814 may includewireless satellite communications devices or other devices with accessto a satellite uplink communications medium. As in the case of DMAservers previously described, a first wireless communications device 812in communication with a first DMA server 810 may wirelessly communicatewith a second wireless communications device 814 is also incommunication with the first DMA server 810.

In addition, because the first DMA server 810 is in communication with aground-based DMA gateway 830 via a suitable uplink communications medium840, the first DMA server 810 is able to route communications betweenthe devices it serves and other devices in communication with the DMAgateway 830. For example, the DMA gateway 830 is in communication with afirst ground-based DMA server 850 that services a first wirelesstelephone device 852. As a result, the wireless communications devices812 and 814 are able to communicate with the first wireless telephonedevice 852. Similarly, the DMA gateway 830 also is in communication witha private IP network 880 that provides communications between the secondsatellite-based DMA server 820 and two ground-based DMA servers 860 and870. As a result, the DMA gateway 830 enables communications between thewireless communications devices 812 and 814 serviced by the firstsatellite-based DMA server 810, the first wireless telephone device 852serviced by the ground-based DMA server 850, a second wireless telephonedevice 862 serviced by a second ground-based DMA server 860, a thirdwireless telephone device 872 serviced by a third ground-based DMAserver 870, and any devices (not shown in FIG. 8) serviced by the secondsatellite-based DMA server 820. In addition, if the DMA gateway 830 werein communication with one or more legacy networks, the DMA gateway 830could enable communications between devices serviced by the legacynetworks and devices serviced by the DMA servers 810, 820, 860, and 870in communication with the DMA gateway 830.

FIG. 9 illustrates a communications network 900 illustrating how acommunications network may include a combination of satellite-based andground-based DMA servers and satellite-based and ground-based DMAgateways. Embodiments of the present disclosure are not restrictive toincluding only ground-based or satellite-based DMA gateways were DMAservers and thus provide flexibility in creating and proliferatingcommunications networks based on the communications needs for which thenetwork is deployed.

A first satellite-based DMA server 910 communicates with wirelesscommunications devices 912 and 914. The first satellite-based DMA server910 also is in communications a satellite communications network 940 anda private IP network 950. Via the satellite communications network 940,first the satellite-based DMA server is able to communicate with asatellite-based DMA gateway 930 to, for example, enable communicationsbetween devices served by a first ground-based DMA server, such as afirst wireless telephone 992. Via the private IP network 950, thesatellite-based DMA server 910 also is able to communicate with otherDMA gateways, such as a first ground-based DMA gateway 960 and a secondground-based DMA gateway 970. Thus, the devices served by thesatellite-based DMA server 910 would be able to communicate with devicesin communication with the ground-based DMA gateways 960 and 970, such asthe second wireless telephone device 974 that is serviced by a secondground-based DMA server 972 in communication with the secondground-based DMA gateway 970. In sum, as described in the particularillustrative embodiments depicted in FIGS. 6-9, satellite-based orground-based DMA servers and satellite-based or ground-based gatewayscan be deployed as desired to enable communications between variouscommunications devices.

To facilitate communications between devices serviced by differentnetworks, the DMA gateways maintain information identifying the devicesthat each services. For example, a user of a wireless telephone deviceserviced by a first DMA server may send a communication to the user ofthe target wireless telephone device that is serviced by a second DMAserver. The first and second DMA servers both are in communication witha DMA gateway that enables communications between the devices servicedby the different DMA servers. The DMA gateway is configured to route thecommunications by accessing information indicating which DMA serversprovide service to which wireless devices. The DMA gateway may maintainthe information locally in the DMA gateway or access informationmaintained in a central register accessible to the DMA gateway. When theinformation is maintained locally in the DMA gateway, DMA gateways inthe network provide information to one another regarding the devicesthey service by exchanging register data describing the devices theyservice. The register data describes devices for which the networks theyservice are the home network as well as for what devices are visiting ontheir networks. This information is exchanged directly between the DMAgateways or through a central database described further below withreference to FIG. 10.

FIG. 10 shows a network 1000 including a pair of DMA gateways 1010 and1050 that facilitate communications between devices on different typesof networks. A first DMA gateway 1010 communicates with a plurality ofDMA servers 1012, 1014, and 1016 and a plurality of legacy networks1020, 1030, and 1040. As described below with reference to FIG. 11, theDMA gateway 1010 includes interfaces configured to communicate with aPSTN 1020, a mobile switching center (MSC) 1030 such as used by wirelesstelephones and communications devices, and a public IP network 1040. TheDMA gateway 1010 thus permits communication between devices serviced bythe DMA servers 1012, 1014, and 1016 and devices serviced by theassociated legacy networks 1020, 1030, and 1040.

In addition, the DMA gateway 1010, through the satellite communicationsnetwork 1080 or other DMA gateway network, communicates with other DMAgateways to support communications between the devices serviced bydifferent DMA gateways. For example, the second DMA gateway 1050 isassociated with a private IP network 1060 that services a plurality ofDMA servers 1052, 1054, 1056 and the devices they serve. Thus, throughthe DMA gateways 1010 and 1050, devices serviced by one of the DMAservers 1012, 1014, and 1016 or devices serviced by the legacy networks1020, 1030, and 1040, can communicate with devices serviced by the DMAservers 1052, 1054, and 1056 or other networks serviced by the secondDMA gateway 1050. The private IP network 1060 also includes a centralregister database 1070 that maintains information serviced by DMAgateways and DMA servers within the network 1000. The operation of thiscentral register database 1070 is described further below.

As shown in FIG. 10, one or more of the DMA servers 1012, 1014, and 1016may communicate directly with a respective DMA gateway, such as DMAgateway 1010, through a satellite uplink or other communications medium.Alternatively, one or other DMA servers 1052, 1054, and 1056 maycommunicate with a DMA gateway, such as DMA gateway 1050, via a privateIP network 1060 in which the DMA servers 1052, 1054, and 1056 and theDMA gateway 1060 participate. When a DMA server communicates with a DMAgateway over a private IP network, the respective DMA server and DMAgateway may communicate with each other by transmitting IP packet dataover the private IP network. On the other hand, when the DMA servercommunicates with the DMA gateway via a different medium, the DMA serverand DMA gateway may communicate with each other according to theprotocol of the available medium.

In the networks of FIGS. 6-10, embodiments of DMA gateways exchangecommunications information identifying devices serviced by one or moreDMA servers or other communications networks that the DMA gatewaysservice. When a DMA gateway detects that it is in communications rangewith one or more DMA servers, the DMA gateway sends communicationsinformation from the DMA servers or other communications networks to oneor more other DMA gateways or to a central database, such as the centralregister database 1070. The communications information may include anotification of what DMA server or servers with which the DMA gateway isin communication. As DMA gateways move between communications ranges ofvarious DMA servers or vice versa, the DMA gateways may send additionalnotifications or other information to update the previously-communicatedcommunications information as to what communications networks areaccessible to the various DMA gateways.

The communications information, in one embodiment, includes registerinformation, such as home location register (HLR) information andvisitor location register (VLR) information maintained by the DMAservers or other communications networks. As described with reference toFIG. 1 and FIG. 2, because a DMA server may include a portable or mobiledevice, the DMA server information also may identify whether the DMAgateway is a home gateway for the DMA server or whether the DMA serveris temporarily registered with the DMA gateway in a visitor DMAregister.

When another DMA gateway receives the DMA server information from afirst DMA gateway, a second DMA gateway stores the DMA serverinformation in a home DMA register in which the second DMA gateway alsostores information regarding the devices it services. The second DMAgateway receives a communication from one of the devices it servicestargeted for a wireless device that is serviced by the first DMAgateway. The second DMA gateway then routes the communication via a DMAgateway network to the first DMA gateway. The first DMA gateway, usingits own home DMA register storing information about the devices isservices, then directs the communication to the network and/or DMAserver that services the targeted communications device.

When the DMA gateway receives DMA server information about one or moreDMA services associated with the DMA gateway or information about othernetworks the DMA gateway services, the DMA gateway may provide the DMAserver information to other DMA gateways in a number of ways. Forexample, the DMA gateway may send a notification to other DMA gatewaysthat is has received the DMA server information and that the DMA serverinformation can be retrieved from the DMA gateway or, as describedbelow, from a central database. The DMA server information is thentransmitted to other DMA gateways in response to queries from one ormore gateways requesting the DMA server information. Alternatively, theDMA gateway may automatically send the DMA server information to othergateways upon receiving the DMA server information.

Instead of or in addition to sending the DMA server information to otherDMA gateways, the DMA gateway may send the DMA server information to acentral database as shown in FIG. 10. Then, for example, when a DMAGgateway such as DMA gateway 1010 is in communications range of a DMAserver such as DMA server 1012, the DMA server information is sent tothe central register database 1070. The DMA server information is sentfrom the DMA gateway 1010 via the satellite communications network 1080to the DMA gateway 1050 where the DMA server information is routed viathe private IP network 1060 to the central register database. Thus, asDMA server networks and other networks are added to the system, the DMAgateway servicing each of these communications networks receives thecommunications information for the communications network and sends thecommunications information to the central register database 1070. Then,other DMA gateways each can receive the new communications informationfrom the central register database 1070.

The new communications information may be automatically sent by thecentral register database 1070 via the DMA gateway 1050 that servicesthe central register database. Alternatively, when new communicationsinformation is received, the DMA gateway receiving the communicationsinformation or the central register database 1070 may send anotification to other DMA gateways that the new information is availablefor retrieval.

FIG. 11 shows an operating environment 1100 including a plurality ofnetworks serviced by a DMA gateway 1102. The DMA gateway 1102 servicesnetworks through a plurality of interfaces configured to supportdifferent types of networks. The DMA gateway 1102 communicates with aprivate IP network 1104, such as that used to communicate with one ormore DMA servers and/or a central register database as shown in FIG. 7,via a data network interface 1106. The DMA gateway 1102 communicateswith the DMA gateway network, which in this example includes a satellitenetwork 1108, via a satellite network interface 1110. In addition, theDMA gateway 1102 includes one or more interfaces that enable the DMAgateway 1102 to communicate with one or more legacy networks. Forexample, the DMA gateway 1102 communicates with a public switchedtelephone network (PSTN) or integrated services digital network (ISDN)1112 via a PSTN/ISDN interface 1114. The DMA gateway 1102 communicateswith a public IP network 1116 via a public IP interface 1118 thatenables the DMA gateway 1102 to, for example, exchange Internet data orvoice over Internet protocol (VoIP) calls. The DMA gateway 1102 alsocommunicates with a wireless network 1120 via a mobile device interface1122. The DMA gateway 1102 also communicates with an ANSI-41 network1124 via an SS7 TCAP/SCCP interface 1126 operable to be used in ISUPsignaling, DMA server identification, roamer registration, and otherfunctions described with reference to the SS7GW interface 522 describedwith reference to FIG. 5.

One or more processors 1130 is coupled with the interfaces 1106, 1110,1114, 1118, and 1122 and a memory device 1140. The memory device 1140may include one or more of a random access memory, including volatileand nonvolatile rewritable memory devices, a read-only memory, and datastorage devices. The memory device 1140 maintains a plurality ofsoftware modules providing executable instructions to the processor 1130to support for the functions of the DMA gateway 1102. The modulesinclude one or more gateway modules 1142 that include the operatingsystem and basic control software that enables the processor 1130 tointeract with its network interfaces. One or more conversion modules1144 control the translation of data and data formats used by one of thenetworks to that of one or more other networks to which data is to becommunicated. One or more routing modules 1146 provide instructions tothe processor for routing communications between the appropriateinterfaces. The routing instructions use information about theaccessibility of devices through various servers, gateways, andnetworks. Thus, as information about a communication is received,routing instructions are provided indicating through which DMA gatewaysthe communication is to be directed from its source to its destination.

One or more legacy network communications modules provide instructionsfor the processor 1130 to interact with each of the legacycommunications network interfaces 1114, 1118, 1122. One or more DMAdetection modules 1152 provide instructions to the processor fordetecting the presence of accessible DMA servers and integrating theservers into the DMA network. One or more register data managementmodules 1154 receive, maintain, and/or forward register data for variousnetworks and devices. The one or more register data management modules1154 are operably coupled with a community location register(CLR)/visitor location register gateway (VLR)/gateway (GW)/global title(GT) (collectively, CVGG) data storage 1160 to maintain register datafor DMA servers and other networks that communicate through the DMAgateway 1102. The register data stored by embodiments according to thepresent disclosure are described below with reference to FIGS. 9 and 10.

The DMA gateway 1102 may be implemented in a number of forms. Forexample, the DMA gateway 1102 may be implemented as an orbitingsatellite, as described with reference to FIGS. 6 and 7. Alternatively,the DMA gateway 1102 may include either a fixed or portable groundstation. The DMA gateways 1102 communicate with each other through agateway network. In the example of FIGS. 6 and 7, the gateway networkincludes a satellite communications network. However, if the DMAgateways include only ground-based stations, the gateway network mayinclude a point-to-point network facilitated by microwavecommunications, optical or other cabled connections, or other types ofcommunications systems. If the gateway network includes both orbitingand ground-based stations, the gateway network may include a combinationof satellite-based and non-satellite based communications systems.

FIGS. 12 and 13 show tables depicting how communications informationincluding register data is stored in the DMA gateways or a centralregister database. The tables in FIGS. 12 and 13 are a logicalrepresentation. The entries within the tables do not represent a singlevalue as might be found, for example, in a single entry of a spreadsheetdocument. Instead, the entries within the rows and columns of the tablerepresent a category of information stored within the table.

In the example of FIGS. 12 and 13, representative data is shown forthree DMA gateways and three DMA servers, although data for any numberof DMA gateways and DMA servers participating in a DMA network may beincluded in register data tables. In this example, it is assumed thateach DMA gateway is in communication with a respective DMA serverdesignated with the same number, e.g., DMA gateway 1 is in communicationwith DMA server 1, etc. FIG. 12 shows tables 1200 and 1250 representingthe register data stored in each of DMA gateway 1 and DMA gateway 2,respectively, while FIG. 10 shows a table 1000 representing the registerdata stored in a central register database for the three DMA gateways.

In the table 1200 for the DMA gateway 1, three rows 1210, 1212, and 1214store register data for each of the respective DMA servers, DMA server1, DMA server 2, and DMA server 3. In a CLR database column 1220, CLRdata is stored for each of the three DMA servers and, in a VLR databasecolumn 1222, VLR data is stored for each of the three DMA servers. InDMAG 2 Community HLR database column 1224 and DMAG 3 Community HLRdatabase column 1226, the HLR data for each of the DMA servers is storedfor DMA gateway 2 and DMA gateway 3, respectively. In a Visitor DMAServer Register column 1228, data is stored for one or more DMA serversthat are temporarily registered with DMA gateway 1.

In the table 1250 for the DMA gateway 2, three rows 1260, 1262, and 1264store register data for each of the respective DMA servers, DMA server1, DMA server 2, and DMA server 3. In a CLR database column 1270, CLRdata is stored for each of the three DMA servers and, in a VLR databasecolumn 1272, VLR data is stored for each of the three DMA servers. InDMAG 1 Community HLR database column 1274 and DMAG 3 Community HLRdatabase column 1276, the HLR data for each of the DMA servers is storedfor DMA gateway 1 and DMA gateway 3, respectively. In a Visitor DMAServer Register column 1278, data for one or more DMA servers that aretemporarily registered with DMA gateway 2.

Referring to FIG. 13, in the table 1300 for the central registerdatabase, three rows 1310, 1312, and 1314 store register data for eachof the respective DMA servers, DMA server 1, DMA server 2, and DMAserver 3. In a DMA gateway 1 HLR database column 1320, HLR data isstored for each of the three DMA servers. In a DMA gateway 1 VLRdatabase column 1322, VLR data is stored for each of the three DMAservers. In DMAG 1 Visitor DMA server register column 1324, data isstored for one or more DMA servers that are temporarily registered withDMA gateway 1. In a DMA gateway 2 HLR database column 1326, HLR data isstored for each of the three DMA servers. In a DMA gateway 2 VLRdatabase column 1328, VLR data is stored for each of the three DMAservers. In DMAG 2 Visitor DMA server register column 1330, data isstored for one or more DMA servers that are temporarily registered withDMA gateway 2.

FIG. 14 shows a flow diagram 1400 of an exemplary process for routingcommunications using DMA gateways. In the example of FIG. 14, a firstDMA server comes in communications range or otherwise becomes accessibleto a first DMA gateway while a legacy communications network becomesaccessible to a second DMA gateway.

At 1402, information is received at a first DMA gateway indicating thelocation of register data for a DMA server. This register data may bestored in another DMA gateway or a central register database. At 1404,information is received indicating that a second DMA gateway is incommunication with a legacy communications network. At 1406, it isdetected that the first DMA server is now in communications range of thefirst DMA gateway. At 1408, the first DMA gateway receives the DMASregister data for the first DMA server from the location identified at1402. As previously described, this information may be automaticallytransmitted to the first DMA gateway when it comes within communicationsrange of the first DMA server or the first DMA gateway may request theinformation from the location where it is stored.

At 1410, information is received that relates to a data and/or voicecommunication placed by a mobile device associated with the first DMAserver. The information indicates that the communication is directed orplaced to a target device accessible via the legacy communicationsnetwork. The accessibility of the legacy communications network to thesecond DMA gateway was previously identified to the first DMA gateway at1404. Thus, at 1412, the communication information is routed from thefirst DMA gateway to the second DMA gateway. The process ends at 1414.The process repeats indefinitely as desired to relay communicationsusing the DMA gateways.

FIG. 15 shows a flow diagram 1500 of an exemplary process for routingcommunications to a DMA gateway depending on whether the DMA gatewaycommunicates with a server through a private IP network or throughanother medium. At 1502, routing instructions are received at a DMAserver from a DMA gateway when the DMA server is in communication withthe DMAG, such as when the DMA gateway comes within communications rangeof the DMA server. At 1504, a communication is received at the DMAserver from a mobile communications device via a wireless transceivercoupled to the DMA server. At 1506, it is determined whether the DMAserver communicates with the DMA gateway via a private IP network. Ifso, at 1510, packet data related to the communication is sent as packetdata over the private IP network that is received by the DMA gateway viaits private IP network interface. On the other hand, if it is determinedat 1506 that the DMA server does not communicate with the DMA gatewayvia a private IP network, at 1512, the information related to thecommunication is transmitted to the DMA gateway via another medium, suchas a direct satellite uplink. The information related to thecommunication is thus received by the DMA gateway via a satellitecommunications network interface.

At 1514, the communication is routed from the DMA gateway to thedestination device. The communication is routed using informationreceived and maintained by the DMA gateway as described, for example, inFIG. 14. The process ends at 1516. The process repeats indefinitely asdesired to relay communications using the DMA gateways.

The above-disclosed subject matter is to be considered illustrative, andnot restrictive, and the appended claims are intended to cover all suchmodifications, enhancements, and other embodiments, which fall withinthe true spirit and scope of the present invention. Thus, to the maximumextent allowed by law, the scope of the present invention is to bedetermined by the broadest permissible interpretation of the followingclaims and their equivalents, and shall not be restricted or limited bythe foregoing detailed description.

1. A method, comprising: receiving at a first distributed mobilearchitecture (DMA) gateway communications information for acommunications network accessible by a second DMA gateway, thecommunications information indicating one or more devices accessible byone of a DMA server and a legacy communications network, wherein thefirst DMA gateway and the second DMA gateway participate in a DMAgateway communications network; storing the communications informationin a home DMA register of the first DMA gateway; receiving acommunication at the first DMA gateway for a target device indicated bythe communications information to be served by the second DMA gateway;and routing the communication from the first DMA gateway to the targetdevice by relaying the communication from the first DMA gateway to thesecond DMA gateway via the DMA gateway communications network.
 2. Themethod of claim 1, wherein: at least one of the first DMA gateway andthe second DMA gateway includes a satellite-based DMA gateway; and theDMA gateway communications network includes a satellite communicationsnetwork.
 3. The method of claim 1, wherein the DMA server includes oneof the group including: a ground-based DMA server; or a satellite-basedDMA server.
 4. The method of claim 1, wherein the communication includesat least one of the group including: a voice communication; or a datacommunication.
 5. The method of claim 1, wherein the legacycommunications network includes one of the group including: a publicswitched telephone network (PSTN); a wireless communications networkserviced by mobile switching center (MSC); a public internet protocol(IP) network; and an American National Standards Institute 41 (ANSI-41)network.
 6. The method of claim 1, further comprising the first DMAgateway sending a notification to the second DMA gateway, thenotification indicating that the communications information is stored atthe first DMA gateway.
 7. The method of claim 1, further comprising,upon receiving the communications information, the first DMA gatewayautomatically sending at least a portion of communications informationto the second DMA gateway via the gateway communications network.
 8. Themethod of claim 1, further comprising, in response to receiving a queryfrom the second DMA gateway for the communications information, thefirst DMA gateway sending at least a portion of the communicationsinformation to the second DMA gateway via the gateway communicationsnetwork.
 9. The method of claim 1, wherein the communicationsinformation includes communications register data including at least oneof the group including: a portion of the community location register; aportion of the home location register (HLR) data for the communicationsnetwork; and a portion of the visitor location register (VLR) for thecommunications network.
 10. The method of claim 9, wherein the registerdata stored at the first DMA gateway indicates that the register data isfor a DMA server temporarily registered in a visitor DMA register of thesecond DMA gateway.
 11. The method of claim 1, further comprising thefirst DMA gateway detecting the presence of the communications networkin a communications range of the first DMA gateway.
 12. The method ofclaim 11, further comprising the first DMA gateway sendingcommunications network information to the second DMA gateway indicatingthat the communications network is within the communications range ofthe first DMA gateway.
 13. The method of claim 11, further comprisingthe first DMA gateway sending communications network information to acentral database indicating that the communications network is in thecommunications range of the first DMA gateway.
 14. The method of claim11, further comprising the first DMA gateway receiving additionalcommunications network information from the second DMA gatewayindicating that the second DMA gateway detects the presence of anadditional communications network within a communications range of thesecond DMA gateway.
 15. The method of claim 1, further comprising thefirst DMA gateway receiving a second notification from a centraldatabase, the second notification indicating that second register datais stored at the central database.
 16. The method of claim 15, furthercomprising the first DMA gateway detecting a second communicationsnetwork in a service area of the first DMA gateway.
 17. The method ofclaim 16, wherein the first DMA gateway detects a private InternetProtocol (IP) network access point in a communications range of thefirst DMA gateway and wherein the first DMA gateway is adapted tocommunicate with the second communications network via the privateInternet protocol (IP) network.
 18. The method of claim 16, wherein thefirst DMA gateway sends second communications information to the centraldatabase indicating that calls associated with the second communicationsnetwork are accessible to the first DMA gateway.
 19. The method of claim18, wherein the first DMA gateway receives second register data from thecentral database.
 20. The method of claim 1, wherein the first DMAgateway receives the communications information from the second DMAgateway.
 21. The method of claim 1, wherein the first DMA gatewayreceives the communications information from a central database.
 22. Anetwork communications system, comprising: a first distributed mobilearchitecture (DMA) gateway including: a first interface adapted tocommunicate with a legacy communications network; a second interfaceadapted to communicate with a private Internet Protocol (IP) network; athird interface adapted to communicate with a DMA gateway communicationsnetwork; and a server having logic adapted to: receive legacy networkinformation from a second DMA gateway, the legacy network informationindicating that the legacy communications network is in a communicationsrange of the second DMA gateway; and forward information associated witha communication received from a DMA server via the second interface tothe second DMA gateway via the third interface; wherein the call isplaced to a destination device accessible via the legacy communicationsnetwork.
 23. The system of claim 22, wherein at least one of the firstDMA gateway and the second DMA gateway comprises a satellite-based DMAgateway.
 24. The system of claim 22, wherein at least one of the firstDMA gateway and the second DMA gateway comprises a ground-based DMAgateway.
 25. The system of claim 22, wherein the DMA server includes oneof the group including: a ground-based DMA server; or a satellite-basedDMA server.
 26. The system of claim 22, wherein the logic is adapted toreceive DMA server register data from the DMA server indicating that amobile communications device is accessible to the DMA server via awireless transceiver coupled to the DMA server.
 27. The system of claim22, wherein the first DMA gateway communicates with a central databasevia the third interface, the central database storing register dataassociated with the DMA server.
 28. The system of claim 22, wherein thefirst DMA gateway communicates with the central database via the secondinterface, the central database storing register data associated withthe DMA server.
 29. The system of claim 22, wherein the first DMAG andthe second DMAG communicate via C-Band, Ku-Band, Ka-Band, L-Band, or anycombination thereof.
 30. The system of claim 22, wherein the gatewaycommunications network at least one of an IP network and a microwavenetwork.
 31. The system of claim 20, wherein the legacy communicationsnetwork includes one or more of the group including: a public switchedtelephone network (PSTN); a wireless network; a public IP network; andan American National Standards Institute 41 (ANSI-41) network.
 32. Thesystem of claim 22, wherein the DMA server is one of a plurality of DMAservers communicating with the first DMAG via the second interface. 33.A method of routing calls via a communications network, the methodcomprising: receiving first routing instructions at a first distributedmobile architecture (DMA) server from a first DMA gateway when the firstDMA server is in a first service area of the first DMA gateway, thefirst DMA gateway comprising a first orbiting satellite; and sending afirst call received at the first DMA server from a first mobilecommunications device via a wireless transceiver integrated with thefirst DMA server to the first DMA gateway via a private InternetProtocol (IP) network according to the first routing instructions;wherein the first call placed to a destination device accessible via alegacy communications network, the legacy communications networkaccessible via the first DMA gateway.
 34. The method of claim 33,wherein the first DMA server is adapted to send the first call whilebeing transported from a first location to a second location.
 35. Themethod of claim 33, wherein the first DMA server receives second routinginstructions from a second DMAG when the first DMA server moves into asecond service area of the second DMAG, the second service areacomprising the second location and the second DMAG comprising anorbiting satellite.
 36. The method of claim 33, wherein the first DMAserver sends a second call received at the first DMA server from thefirst mobile communications device to the second DMA gateway via theprivate IP network according to the second routing instructions.
 37. Themethod of claim 36, wherein the second call is associated with adestination device accessible via the legacy communications network. 38.The method of claim 36, wherein the second call is associated with asecond mobile communications device accessible to a second DMA server,the second DMA server accessible to the second DMA gateway via theprivate IP network.
 39. The method of claim 33, wherein the first DMAserver receives the second routing instructions from the second DMAGduring the first call.
 40. The method of claim 33, wherein the first DMAserver sends first DMA server register data to the second DMA gateway inresponse to receiving the second routing instructions.
 41. The method ofclaim 33, wherein the first DMA server receives second routinginstructions from a second DMA gateway when the first DMA server leavesthe first service area and enters a second service area of the secondDMA gateway due to orbital motion of the first DMA gateway and thesecond DMA gateway, the second DMA gateway comprising an orbitingsatellite.
 42. A network communications system, comprising: adistributed mobile architecture (DMA) server coupled to a wirelesstransceiver, the DMA server including: a first interface adapted tocommunicate with a private Internet Protocol (IP) network; a secondinterface adapted to communicate with a gateway communications network;and a server having logic adapted to: receive a call from a mobilecommunications device via the wireless transceiver; and send callinformation related to the call to a DMA gateway, the DMA gateway;wherein the call is placed to a destination device accessible via alegacy communications network, the legacy communications networkaccessible via the DMA gateway.
 43. The system of claim 42, wherein thelogic is adapted to send the call information to the DMA gateway via thefirst interface according to routing instructions received at the DMAserver from the DMA gateway.
 44. The system of claim 42, wherein thelogic is adapted to send the call information to the DMA gateway via thesecond interface according to routing instructions received at the DMAserver from the DMA gateway.
 45. The system of claim 42, wherein thelogic is adapted to convert the call information to packet data when thecall information is sent to the DMAG via the first interface.
 46. Anorbiting satellite, comprising: a first interface adapted to communicatewith a legacy communications network; a second interface adapted tocommunicate with a private Internet Protocol (IP) network; and a serverhaving logic adapted to: receive a call via the first interface, thecall placed to a first mobile communications device accessible to afirst distributed mobile architecture (DMA) server; and route the callto the first DMA server via the second interface, wherein the first DMAserver includes a wireless transceiver to communicate with the firstmobile communications device.